-
Notifications
You must be signed in to change notification settings - Fork 83
5.0.1 & 4.6.23 releases #2880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 5.0
Are you sure you want to change the base?
5.0.1 & 4.6.23 releases #2880
Conversation
Preview of modified filesPreview of modified Markdown: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall, just a couple of suggestions
Could you also bump the variables in user doc? https://github.com/ibexa/documentation-user/blob/5.0/mkdocs.yml#L196-L197
docs/release_notes/ibexa_dxp_v5.0.md
Outdated
#### Pagination for ibexa_object_relation_list in GraphQL | ||
|
||
To improve performance and gain greater control over the returned responses from the [GraphQL API](graphql.md), you can now [enable pagination](relationlistfield.md#enable-pagination-in-graphql) of relations specified using the RelationList field type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see https://doc.ibexa.co/en/5.0/content_management/field_types/field_type_reference/relationlistfield/#enable-pagination-in-graphql (and #2874)
The parameter is removed, the pagination is enabled by default.
I'd remove this section (or just mention that the pagination is enabled by default)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this section in 4c10a72 as this is not a change from 5.0.1
#### Pagination for ibexa_object_relation_list in GraphQL | ||
|
||
To improve performance and gain greater control over the returned responses from the [GraphQL API](graphql.md), you can now [enable pagination](relationlistfield.md#enable-pagination-in-graphql) of relations specified using the RelationList field type. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could mention the changes to discounts as well - on v5 it's no longer an LTS update, so the same changes could be mentioned here (I mean:
documentation-developer/docs/release_notes/ibexa_dxp_v4.6.md
Lines 44 to 54 in c2696b7
#### Global discount codes limits | |
- You can now [limit the number of times](discounts_guide.md#discount-codes) a discount code can be used before it expires. The discounts created before this release are set to unlimited global usage | |
#### Discount codes prioritization | |
- Discounts with discount codes now have priority over the other discounts | |
#### Discount codes migrations | |
- You can now create discount codes using [data migrations](importing_data.md#discount-codes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs/release_notes/ibexa_dxp_v5.0.md
Outdated
|
||
To improve performance and gain greater control over the returned responses from the [GraphQL API](graphql.md), you can now [enable pagination](relationlistfield.md#enable-pagination-in-graphql) of relations specified using the RelationList field type. | ||
|
||
#### Other upgrades |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually I tried to mention new PHP API changes, for example:
documentation-developer/docs/release_notes/ibexa_dxp_v4.6.md
Lines 33 to 38 in c2696b7
#### PHP API | |
The PHP API has been enhanced with the following new classes: | |
- [`Ibexa\Contracts\ProductCatalogSymbolAttribute\Search\Criterion\SymbolAttribute`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalogSymbolAttribute-Search-Criterion-SymbolAttribute.html) | |
- [`Ibexa\Contracts\ProductCatalogSymbolAttribute\Value\ChecksumInterface`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalogSymbolAttribute-Value-ChecksumInterface.html) |
We could mention the 3 new classes from #2882 (comment) (skipping Collaboration for now)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 4c10a72
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small remark.
Don't take the second comment into account, as it's not part of the scope of this PR (I wanted to delete the comment, but due to a technical problem I can't).
Co-authored-by: julitafalcondusza <[email protected]>
Thank you for the review. Variables were increased in 8477d3b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
The variables are correctly bumped here, in the dev doc. I meant the user documentation, which has its own set of variables: https://github.com/ibexa/documentation-user/blob/5.0/mkdocs.yml#L196-L197 |
Note: To list the classes affected by stricter method signature type hinting is time consuming, and the resulting list itself will be too long to be useful to the reader.
Related PR: ibexa/documentation-user#372
Checklist